What

• Add `GetVaultConfigOptions`, `VaultProvider`, `VaultConfig`, `ConcreteVaultConfig`, `ConcreteDepositResult` types to `iDefiVault.ts`
• Update `DepositResult` to a discriminated union: `{ pendingApprovalId, state }` (concrete_btccx) | `{ operationId, txRequestIds }` (morpho)
• Add `getVaultConfig` to the `IDefiVault` interface
• Add `defiParams: t.unknown` to the `BuildParams` whitelist so the field passes through `prebuildWhitelistedParams()`
• Add optional `defiParams` field to `SendManyOptions` for discoverability
• Bump `@bitgo/public-types` to `^6.39.0` (picks up `defiParams` on `TxSendBody`)

Why

• CB-1.8 requires `depositToVault` to support Concrete BTCcx vaults in addition to Morpho. Resolving the provider from vault config requires a new `getVaultConfig` method and new types for the Concrete response shape (a `pendingApproval`, not a txRequest)
• `defiParams` must be whitelisted in `BuildParams` or it gets stripped by `prebuildWhitelistedParams()` before reaching WP

Test plan

• Build passes: `yarn build` in `modules/sdk-core`
• No TypeScript errors on the changed files

Stack

This PR is part 1 of 2 in a stack. Review and merge in order:

1. feat(sdk-core): add VaultConfig types and defiParams to BuildParams/SendManyOptions #9205 — types + interfaces + dependency bump (base: `master`) ← you are here
2. feat(sdk-core): add getVaultConfig and Concrete BTC deposit path to DefiVault #9206 — core logic + tests (base: `pt1`)

Ticket: DEFI-279